Mobile device inactive mode and inactive mode verification

ABSTRACT

A mobile device, comprising: a processor; and a memory including instructions that when executed by the processor cause it to perform the steps of: receiving a user selection to automatically enter an inactive mode in response to an action within the mobile device indicating the device is being used in a moving vehicle; receiving a communication from a wireless communication module; if the mobile device is not in inactive mode, providing a notification to the user that a communication has been received; if the mobile device is in inactive mode, transmitting an away message via the wireless module.

BACKGROUND OF THE INVENTION

The present subject matter relates generally to a mobile device including functionality for suppressing user notifications of communications received by the mobile device and notifying the sender of the communication that the user is not receiving communications. Further, the present subject matter relates generally to systems and methods for verifying that a user was not receiving communications during a particular period of time.

User distraction caused by mobile devices has become a serious problem in modern society. For example, motor vehicle accidents caused by distracted driving are on the rise and have become as serious as driving while intoxicated. Many drivers are aware of the risks of distracted driving but may lack the resolve to avoid trying to respond to incoming communications. One previous solution was to power down the mobile device while driving, however, this is inconvenient and easy to forget to initiate. Further, powering down the device may block access to urgent communications that may need to be received. What are needed are mechanisms to limit user communication distractions without forcing the user to power down a mobile device and miss essential communications.

Further, the proliferation of accidents cause by distracted driving has created a need to prove that one was not operating a communications device during operation of a vehicle. What are needed are mechanisms to show that a user was not using a communications device during an accident while operating a vehicle.

Accordingly, there is a need for a mobile device including functionality for suppressing communications to a user and systems for verifying that a user was not receiving communications during a particular period of time, as described herein.

BRIEF SUMMARY OF THE INVENTION

To meet the needs described above and others, the present disclosure provides a mobile device including functionality for suppressing communications to a user and systems for verifying that a user was not receiving communications during a particular period of time.

As used herein, a communication may include a mobile device call, SMS text message, email, application notification, etc. A sender includes an individual sending the communication.

An inactive mode for a mobile device as disclosed herein may be implemented using stored instructions that implement the functionality disclosed herein. In a preferred embodiment, the stored instructions may be provided in the form of a mobile device application. A user may install the mobile device application through a mobile device application online store.

A user may enable an inactive mode of the device to suppress notification of incoming phone calls, text, emails, etc. and automatically notify the sender with an away message. By suppressing the communications distracted driving may be reduced. One drawback, however, is that senders may feel upset that they are not being answered when the sender is expecting the user to reply. Thus, in order to reassure senders that they will receive a response at the earliest convenient opportunity, the mobile device permits the user to send an away message upon receipt of a communication.

Further, the device may communicate with a certification server to “certify” that a mobile device was not operational during a certain period as evidence that the phone was not used during driving. By enabling a user to show that he or she did not use mobile device during operation of a vehicle, he or she may be able to qualify for discounts from an insurance company or may be able to show he or she was not at fault in an accident. Further, parents may use such records to verify that teenage drivers are not being distracted by their mobile device.

In an embodiment, a method carried out by a mobile device to provide for an inactive mode and thus prevent distracted driving includes the steps of: placing the mobile device in inactive mode; detecting one or more incoming communications; suppressing notification of the user of the one or more incoming communications; transmitting an away message to one or more senders of the one or more communications; and notifying the user of missed communications upon completion of the inactive mode.

The method begins when the mobile device is placed in inactive mode. The inactive mode may be activated by many different mechanisms. For example, a user may press a button to begin the inactive mode. Alternatively, a user may schedule a time period during which the mobile device is automatically in inactive mode. Even further, inactive mode may be automatically initiated upon the use of a driving directions functionality of the mobile device. Yet even further, the inactive mode may be automatically initiated upon the pairing of the mobile device and a vehicle. Moreover, inactive mode may be activated by a remote user, for example, to enable parents to limit distracted driving by teenagers. Additionally, the inactive mode may be activated by the mobile device detecting a particular location using GPS, such as a gym or school, where inactive mode is routinely activated. It is contemplated that any input that indicates that the user is not to be distracted may be used to place the device in inactive mode, as will be understood by those of skill in the art.

While in inactive mode, the mobile device will detect incoming communications. When inactive mode functionality is provided as a mobile application, the mobile application may register with the operating system of the mobile device to receive a notification upon a communication event, such as a mobile call, SMS message, or email. Upon receipt of notification of the incoming communication, the mobile application may capture contact information of the sender, such as phone number or email address.

In addition to suppressing communications, inactive mode may restrict the user's use of the mobile device. For example, the user of the mobile device may be restricted from accessing a web browser on the mobile device. Inactive mode may restrict all use of the mobile device or may permit only selective access to needed functionality. For example, when driving, mapping and navigation functionality may remain accessible.

It is contemplated that the user may customize the allowed functionality during inactive mode. Alternatively or additionally, the restriction on the functionality may be pre-programmed in the device, for example, if the inactive mode functionality is embodied in a mobile application distributed by an insurance company, the restriction of functionality may be optimized to minimize distracted driving accidents. Further, a remote user may restrict the functionality of the device. For example, a parent may limit a child's use of a mobile device during nighttime sleeping hours.

Upon receiving notification of a communication event, the mobile device may suppress normal user notification. The mobile device may suppress normal user notification actions, such as ringing, vibration, and screen activation. Further the mobile device may suppress applications normally launched upon a communication event, such as a mobile call application. In some embodiments, the mobile device may permit normal user notification if the sender is on a pre-screened list of allowed senders.

After suppressing user notification, the mobile device may transmit an away message to the sender. The away message may be sent via the same medium that the original communication was made in. For example, if a text message was received, the mobile device may transmit a response via text message. Alternatively, the message may be sent by a different medium. For example, if a phone call was received, the mobile device may transmit the away message via text message or email (if, for example, the sender has an associated email address in the users contacts). It is further contemplated that the user's inactive mode away message may be automatically shared to social networks such Facebook and Twitter upon activation of the inactive mode.

The user may configure an away message before placing the mobile device in inactive mode. The user may configure multiple away messages and choose among the away messages when placing the mobile device in away mode.

At the appropriate time, the device may leave inactive mode and permit the user to use the full functionality of the device. In an embodiment, inactive mode may be disabled by pressing a button ending inactive mode. Alternatively, where inactive mode was scheduled to start automatically, the mobile device may leave inactive mode by reaching the end of a scheduled time. Further, where the mobile device was placed in inactive mode by the driving directions functionality, the mobile device may leave inactive mode by arriving at a destination. Even further, where the mobile device was placed in inactive mode remotely, the mobile device may be removed from inactive mode by remote deactivation, etc. It will be apparent to one of skill in the art that that the mobile device may be removed from inactive mode by any mechanism that reflects that the need for restricted access is no longer needed.

Upon completion of the inactive mode, the mobile device notifies user of missed communications. The user may then view any text messages or emails, or may listen to voicemails left by the sender.

As described, the device may “certify” or prove that a mobile device was not operational during a certain period as evidence that the phone was not used during driving. A method of proving a cell phone was disabled comprises the steps of: receiving an input by the mobile device to begin the inactive mode; transmitting an inactive mode begin notification from the mobile device to the certification server; receiving, by the certification server, an inactive mode begin notification; suppressing notifications to a user; receiving an input by the mobile device to end the inactive mode; transmitting an inactive mode end notification from the mobile device to the certification server; receiving an inactive mode end notification by the certification server; generating, by the certification server, a certified record of the time of the inactive mode begin notification and the inactive mode end notification.

The method of proving a cell phone was disabled may begin upon the mobile device being placed in inactive mode. As previously described, the mobile device may be placed in inactive mode by the user pressing a button to begin the inactive mode; by the user scheduling a time period during which the mobile device is automatically in inactive mode; by the use of the driving directions functionality of the mobile device; by activation by a remote user; etc.

Upon being placed in inactive mode, the mobile device may transmit an inactive mode begin notification to the server. The inactive mode begin notification may include a user identifier, and a begin timestamp indicating the time that the inactive mode was initiated. Further, the inactive mode begin notification may include a listing of functionality permissions to record the functionality made available and/or the functionality made restricted to the user during the inactive mode. It is contemplated that the mobile device need not immediately transmit the inactive mode begin notification upon the step of receiving an input to begin inactive mode is received, and the mobile device may alternatively transmit the inactive mode begin notification when requested, when a connection is available, during periods of low bandwidth utilization, or any other time useful to create the certification.

The certification server receives the inactive mode begin notification from the mobile device. The certification server may assume that inactive mode is operating continuously until receiving a signal, such as an inactive mode end notification, that inactive mode has been disabled. A certified record of the data contained in the inactive mode begin notification may be created and stored in a database of the certification server. The certified record may include a first timestamp of the time the inactive mode begin notification was received.

In inactive mode, the mobile device may suppress communications and enforce the restrictions of the inactive mode until the step of receiving an input to end inactive mode. As previously described, an input may be the user pressing a button to end the inactive mode, the user scheduling a time period during which the mobile device is automatically in inactive mode, the use of the driving directions functionality of the mobile device, activation by a remote user; etc.

At the conclusion of inactive mode, the mobile device may transmit an inactive mode end notification to the certification server to indicate that the device has left the inactive mode. The inactive mode end notification may include a user identifier and a end timestamp marking the time that the mobile device was removed from inactive mode. Further, the inactive mode end notification may include a listing of functionality permissions to record the functionality made available and/or the functionality made restricted to the user during the inactive mode. It is contemplated that the mobile device need not immediately transmit the inactive mode end notification upon the step of receiving an input to begin inactive mode is received, and the mobile device may transmit the inactive mode end notification when requested, when a connection is available, during periods of low bandwidth utilization, or any other time useful to create the certification.

The certification server may receive an inactive mode end notification from the mobile device. Upon receipt of the inactive mode end notification, the certification server may make a certified record of the inactive mode session. The certified record of the inactive mode session may include the inactive mode begin notification, an inactive mode begin notification arrival timestamp recording the arrival of the inactive mode begin notification, the inactive mode end notification, and an inactive mode end notification arrival timestamp recording the arrival of the inactive mode end notification. The record may be used to verify that the inactive mode was enabled during a period of time. To do so, the record may be made available via a user interface to the user, an insurance company, the police, the courts, a parent of the user, etc., to certify the times the device was in inactive mode and the restrictions on functionality in place during inactive mode.

In an embodiment, a mobile device includes: a processor; and a memory including instructions that when executed by the processor cause it to perform the steps of: receiving a user selection to automatically enter an inactive mode in response to an action within the mobile device indicating the device is being used in a moving vehicle; receiving a communication from a wireless communication module; if the mobile device is not in inactive mode, providing a notification to the user that a communication has been received; and if the mobile device is in inactive mode, transmitting an away message via the wireless module.

In some embodiments of the mobile device, the action is the activation of a driving directions functionality. In other embodiments, the action is GPS location functionality detecting a velocity above a certain rate. In additional embodiments, the action is pairing the mobile device with the moving vehicle.

In some embodiments of the mobile device, the communication is a mobile phone call. In other embodiments, the away message is one of a mobile phone call, an SMS message, or an email. In additional embodiments the communication is an SMS phone call. In further embodiments, the communication is an email.

In some embodiments of the mobile device, the memory further includes instructions that when executed by the processor cause it to perform the steps of: receiving an input from a user requesting access to a function of the mobile device; if the mobile device is not in inactive mode, providing access to the requested functionality; and if the mobile device is in inactive mode, checking if the requested functionality is present on a list of restricted functionality, and if the requested functionality is present on a list of restricted functionality, refusing access to the requested functionality.

In an embodiment, a communication system includes: a first mobile device in communication with a second mobile device to control communications between the second mobile device and sending devices; wherein the first mobile device includes: a first user interface; a first wireless communications module; a first processor, controlling the first wireless communications module and the first user interface; and a first memory controlled by the first processor, the first memory including instructions that when executed by the first processor cause the first processor to perform the steps of receiving, via the first user interface, a trigger condition including a trigger selected from the group including contact group triggers, time triggers, location triggers, and communication type triggers, transmit to the second mobile device, via the first wireless communications module, the trigger condition, wherein the second mobile device includes: a second wireless communications module; a second processor, controlling the second wireless communications module; and a second memory controlled by the second processor, the second memory including instructions that when executed by the second processor cause the second processor to perform the steps of receiving the trigger condition from the first mobile device via the second wireless communications module, in response to receiving an incoming communication from the second wireless communications module that satisfies the trigger condition, placing the second mobile device in an inactive mode by suppressing one or more sound, visual, or vibration communication cues that would have accompanied the incoming communication had the second mobile device not been in the inactive mode.

In an embodiment, the second device includes a user interface, wherein the second processer receives, via the user interface, a user selection of an away message to use when the mobile device is in inactive mode, wherein, in response to receiving an incoming communication from the second wireless communications module that satisfies the trigger condition, the second processor, via the second wireless communications module, transmits the user selected away message to the sender of the incoming communication.

In an embodiment, the trigger condition includes a contact group trigger including a selected contact group, wherein the incoming communication satisfies the trigger condition when the incoming communication originates from a member of the selected contact group. Additionally, in an embodiment, the trigger condition includes a time trigger including a selected time period, wherein the incoming communication satisfies the trigger condition when the incoming communication is received within the selected time period. Moreover, in an embodiment, the trigger condition includes a location trigger including a selected location, wherein the incoming communication satisfies the trigger condition when the incoming communication is received while the mobile device is located at the selected location. Further, in an embodiment, the trigger condition includes a communication type trigger including a selected communication type, wherein the incoming communication satisfies the trigger condition when the incoming communication is a communication of the selected communication type.

In an embodiment, a mobile device includes: a wireless communications module; a processor, controlling the wireless communications module; and a memory controlled by the processor, the memory including instructions that when executed by the processor cause the processor to perform the steps of: providing a graphical user interface through which a user customizes one or more functions of the mobile device when placed in an inactive mode; receiving a trigger condition including a trigger selected from the group including contact group triggers, time triggers, location triggers, and communication type triggers, receiving a user selection of an away message to use when the mobile device is in the inactive mode; in response to receiving an incoming communication from the wireless communications module that satisfies the trigger condition, transmitting the user selected away message via the wireless communications module and suppressing one or more sound, visual, or vibration communication cues that would have accompanied the incoming communication had the mobile device not been in the inactive mode.

In an embodiment, a mobile device includes: a user interface including a silence button that, when pressed, silences one or more sound, visual, or vibration communication cues accompanying a communication; a wireless communications module; a processor, controlling the wireless communications module and the user interface; and a memory controlled by the processor, the memory including instructions that when executed by the processor cause the processor to perform the steps of: receiving a user selection of an away message to use when the mobile device is in an inactive mode; receiving, via the user interface, a minimum silences threshold; receiving, via the user interface, a communication type threshold, contact group threshold, time period threshold, and location threshold, wherein the communication type threshold, contact group threshold, time period threshold, and location threshold define a plurality of bins, wherein each bin of the plurality of bins corresponds to a trigger condition, in response to receiving, via the user interface, a plurality of indications that the silence button has been pressed in response to a communication cue signifying an incoming communication, assigning each indication to one of the plurality of bins corresponding to a communication type, a contact group, a time period, and a location associated with the indication, when a number of the plurality of indications assigned to a bin of the plurality of bins exceeds the minimum silences threshold, activate a trigger condition corresponding to the bin, in response to receiving an incoming communication from the wireless communications module that satisfies the activated trigger condition, transmitting, via the wireless module, the user selected away message to a sender of the incoming communication and suppressing one or more sound, visual, or vibration communication cues that would have accompanied the incoming communication.

One objective of the invention is to increase driver safety by reducing mobile device communications as a source of distraction.

A further objective is to inform callers of the delay and the reason for failing to respond.

Another objective of the invention is to provide a mechanism for users to prove that the communication functions of their mobile device were disabled at a particular time.

Additional objects, advantages and novel features of the examples will be set forth in part in the description which follows, and in part will become apparent to those skilled in the art upon examination of the following description and the accompanying drawings or may be learned by production or operation of the examples. The objects and advantages of the concepts may be realized and attained by means of the methodologies, instrumentalities and combinations particularly pointed out in the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawing figures depict one or more implementations in accord with the present concepts, by way of example only, not by way of limitations. In the figures, like reference numerals refer to the same or similar elements.

FIG. 1 is a schematic view of the ecosystem of a device including functionality for suppressing communications to a user using an inactive mode and a verification system to verify that a user was not receiving communications during a particular period of time.

FIG. 2 is a diagram of an example of a device including functionality for suppressing communications to a user using an inactive mode and verifying that a user was not receiving communications during a particular period of time.

FIG. 3 is a flow chart illustrating a method carried out by a mobile device to provide for an inactive mode.

FIG. 4a is an example mobile device user interface showing a start screen used to begin the inactive mode.

FIG. 4b is an example mobile device user interface showing a scheduling screen to schedule a time period during which the mobile device is automatically in inactive mode.

FIG. 4c is an example mobile device user interface showing a GPS/directions screen that when opened may trigger the inactive mode.

FIG. 4d is a front view of a mobile device user interface showing a Bluetooth device detection screen that when used to accept a Bluetooth connection may trigger the inactive mode.

FIG. 5a is an example mobile device user interface showing a custom message selection screen.

FIG. 5b is an example mobile device user interface showing a custom message creation screen.

FIG. 5c is an example mobile device user interface showing a custom message selection screen including example away messages.

FIG. 5d is an example mobile device user interface showing a start screen that includes a custom away message.

FIG. 6 is an example mobile device user interface showing a notification screen displayed upon leaving inactive mode.

FIG. 7 is a flow chart illustrating a certification method to create a certified record at the certification server that a mobile device was inactive during a particular time.

FIG. 8a is a diagram of an example inactive mode begin notification created during the execution of the certification method of FIG. 7.

FIG. 8b is a diagram of an example inactive mode end notification created during the execution of the certification method of FIG. 7.

FIG. 8c is a diagram of an example record of an inactive mode session created during the execution of the certification method of FIG. 7.

FIG. 9 illustrates a trigger definition screen to enable a use to define triggers to place the mobile device in an inactive mode.

FIG. 10 illustrates a response definition screen 750 to permit the user to define a response to a communication suppressed by a trigger.

FIG. 11 illustrates an add exceptions screen to permit the user to define triggers that permit otherwise suppressed communications to get through.

FIG. 12 illustrates a rules screen that lists the inactive mode rules, such as triggers and exceptions, that are currently active.

FIG. 13 illustrates an example of an inactive mode system including a mobile device of a user and associated mobile devices of associated users that are associated with the user.

FIG. 14 illustrates a “homework mode” control screen to permit the user of the mobile device to control an associated devices' receipt of calls, messages, emails, etc.

FIG. 15 illustrates an alert screen on an associated device that has been placed into a “homework mode” by the mobile device.

FIG. 16 illustrates an automatic rules configuration screen to permit the user to enable automatic rule generation and configure the settings of the automatic rule generation.

FIG. 17 illustrates a generated rules screen listing automatically generated rules based on the settings defined using the automatic rules configuration screen.

FIG. 18 is an example mobile device user interface showing a start screen used to begin the inactive mode via a silence button.

FIG. 19 is a flowchart which illustrates how a mobile device may in response to receiving, via the user interface, a plurality of indications that the silence button has been pressed in response to a communication cue signifying an incoming communication, assign each indication to one of a plurality of bins corresponding to a communication type, a contact group, a time period, and a location associated with the indication.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 illustrates the ecosystem 10 of an example of a mobile device 100 including functionality for suppressing communications using an inactive mode. As shown in FIG. 1, the ecosystem 10 includes a communications network 40 which provides communications functionality to the mobile device 100, other communication devices 20 which other users may use to communicate to the mobile device 100, and a certification server 30 that may verify that a user 15 was not receiving communications during a particular period of time.

A user 15 may enable an inactive mode of the device 100 to suppress notification of incoming phone calls, text, emails, and other communications and automatically notify the device 20 of the sender 17 with an away message. By suppressing the incoming communications, the mobile device 100 may minimize user distractions permitting the user 15 to maintain concentration on important tasks, such as driving. One drawback, however, is that senders 17 may feel upset that they are not being answered when the sender 17 is expecting the user 15 to answer communications. Thus, in order to reassure senders 17 that their communication will receive a response at the earliest convenient opportunity, the mobile device 100 permits the user 15 to send an away message upon receipt of a communication.

FIG. 2 is a block diagram of an example implementation of a mobile device 100 including an inactive mode. The mobile device 100 includes communication functions that can be facilitated through one or more wireless communication subsystems 120, which can include radio frequency receivers and transmitters and/or optical (e.g., infrared) receivers and transmitters. The specific design and implementation of the communication subsystem 120 can depend on the communication network(s) over which the mobile device 100 is intended to operate. For example, the mobile device 100 can include communication subsystems 120 designed to operate over a GSM network, a GPRS network, an EDGE network, a Wi-Fi or WiMax network, and a Bluetooth network. In particular, the wireless communication subsystems 120 may include hosting protocols such that the mobile device 100 may be configured as a base station for other wireless devices.

A memory 138 may store communication instructions 142 to facilitate communicating with one or more additional devices, one or more computers and/or one or more servers. The memory 138 may include phone instructions 148 to facilitate phone-related processes and functions; short message service instructions 150 to facilitate SMS-messaging related processes and functions; electronic mail instructions 151 to facilitate electronic-mail processes and functions. The phone instruction 148, the short message service instructions 150, electronic mail instructions 151 may include default instructions to notify a user via sound, visual, or vibration cues to alert the user of incoming communications. The memory may further include inactive mode instructions 147 to suppress the sound, visual, or vibration communication cues and manage the inactive mode related processes and functions further described herein.

Turning to FIG. 3, in an embodiment, a method 300 carried out by a mobile device 100 to provide for an inactive mode includes: the step 301 of placing the mobile device 100 in inactive mode; the step 302 of detecting one or more incoming communications; the step 303 of suppressing notification of the user 15 of the one or more incoming communications; the step 304 of transmitting an away message to one or more senders 17 of the one or more communications; and the step 305 of notifying the user 15 of missed communications upon completion of the inactive mode.

The method 300 begins at step 301 when the mobile device 100 is placed in inactive mode. Inactive mode may be activated by many different mechanisms. For example, as shown in FIG. 4a , a user 15 may press a start button 510 on a start screen 520 to begin the inactive mode. Alternatively, a user 15 may select the set timer button 515 on the start screen 515 to enter a scheduling screen 530, as shown in FIG. 4b , to schedule a time period during which the mobile device 100 is automatically in inactive mode. Even further, as shown in FIG. 4c , the inactive mode may be automatically initiated upon the opening of a GPS/directions screen 540 of the mobile device. Yet even further, as shown in FIG. 4d , the inactive mode may be automatically initiated upon the pairing of the mobile device 100 and a vehicle, as shown by the Bluetooth device detection screen 550. Moreover, the inactive mode may be activated by a remote user 15, for example, to enable parents to limit distracted driving by teenagers. Additionally, the inactive mode may be activated by the mobile device 100 detecting a particular location using GPS, such as a gym or school, where inactive mode is routinely activated. It is contemplated that any input that may indicate that the user is not to be distracted may be used to place the device in inactive mode, as will be understood by those of skill in the art.

Once placed in inactive mode, at step 302, the mobile device 100 will detect any incoming communications normally. When inactive mode functionality is provided as a mobile application 141, upon entering inactive mode the mobile application 141 may register with the operating system of the mobile device 100 to receive a notification upon a communication event, such as a mobile call, SMS message, or email. Upon receipt of notification of the incoming communication, the mobile application 141 may capture contact information of the sender 17, such as phone number or email address.

Proceeding to step 303, upon receiving notification of an incoming communication, the mobile device 100 may suppress normal user notification. The mobile device 100 may suppress normal user notification actions, such as ringing, vibration, and screen activation. Further the mobile device 100 may suppress applications normally launched upon a communication event, such as a mobile call application. In some embodiments, the mobile device 100 may permit normal user notification if the sender 17 is on a pre-screened list of allowed senders 17.

After suppressing user notification of an incoming communication, the mobile device 100, at step 304 of the method 300, may transmit an away message 575 to the sender 17. The user 15 may configure multiple away messages 575 and choose among the away messages 575 when placing the mobile device 100 in away mode. As shown in FIGS. 5a-5d , the user 15 may configure an away message before placing the mobile device 100 in inactive mode. FIG. 5a illustrates an away message selection screen 560 before the user 15 has set up an away message 575. A user 15 may select the away message creation button 565 to enter an away message editing screen 570 including an edit box 572, as shown in FIG. 5b . After creating away messages 575, the user 15 may select from the away messages 575 tin the away message selection screen 560 as shown in FIG. 5c . Upon selecting an away message 575, the start screen 520 is opened permitting the user to start the inactive mode. It is further contemplated that the away message 575 may be automatically shared to social networks such Facebook and Twitter upon activation of the inactive mode.

In some embodiments, the away message 575 may be sent via the same communications medium in which the original communication was made. For example, if a text message was received, the mobile device 100 may transmit the away message 575 via text message. Alternatively, the away message 575 may be sent by a different communications medium. For example, if a phone call was received, the mobile device 100 may transmit the away message 575 via text message or email.

Upon completion of the inactive mode, next at step 305, the mobile device 100 notifies the user 15 of missed communications. At the missed communications screen 580 shown in FIG. 6, the user 15 may then view any text messages or emails by clicking the view message button 585, listen to voicemails left by the sender 17 by clicking the view calls button 587, or otherwise use the full functionality of the device. In an embodiment, inactive mode may be disabled by pressing a button ending inactive mode. Alternatively, where inactive mode was scheduled to start automatically, the mobile device 100 may leave inactive mode by reaching the end of a scheduled time. Further, where the mobile device 100 was placed in inactive mode by the driving directions functionality, the mobile device 100 may leave inactive mode by arriving at a destination. Even further, where the mobile device 100 was placed in inactive mode remotely, the mobile device 100 may be removed from inactive mode by remote deactivation. It will be apparent to one of skill in the art that that the mobile device 100 may be removed from inactive mode by any mechanism that reflects that the need for restricted access is no longer needed.

In addition to suppressing communications, inactive mode may restrict the user's use of the mobile device. For example, the user 15 of the mobile device 100 may be restricted from accessing a web browser, applications, communications programs, etc. Inactive mode may restrict all use of the mobile device 100 or may permit only selective access to certain functionality. For example, when driving, mapping and GPS/navigation functionality may remain accessible.

It is contemplated that the user 15 may customize the allowed functionality during inactive mode. Alternatively or additionally, the restriction on the functionality may be pre-programmed in the inactive mode instructions 147. For example, if the inactive mode functionality of the mobile device 100 is embodied in a mobile application 141 distributed by an insurance company, the restriction of functionality may be optimized to minimize distracted driving accidents. Further, a remote user may restrict the functionality of the mobile device 100. For example, a parent may limit a child's use of a mobile device 100 during nighttime sleeping hours.

Referring to FIG. 4, the certification method 400 may be used to create a certified record 670 (FIG. 6c ) by the certification server 30 that records that a mobile device 100 was inactive during a particular time. As shown in FIG. 4, the certification method 400 includes: the step 401 of receiving an input by the mobile device 100 to begin the inactive mode; the step 402 of transmitting an inactive mode begin notification 610 from the mobile device 100 to the certification server 30; the step 403 of receiving, by the certification server 30, an inactive mode begin notification 610; the step 404 of suppressing notifications to a user 15; the step 405 of receiving an input by the mobile device 100 to end the inactive mode; the step 406 of transmitting an inactive mode end notification 650 from the mobile device 100 to the certification server 30; the step 407 of receiving an inactive mode end notification 650 by the certification server 30; the step 408 of generating, by the certification server 30, a certified record 670 of the time of the inactive mode begin notification 610 and the inactive mode end notification 650.

The certification method 400 may begin upon the step 401 of the mobile device 100 receiving an input to begin the inactive mode. For example, as shown in FIG. 4a , a user 15 may press a start button 510 on a start screen 520 to begin the inactive mode. Alternatively, a user 15 may select the set timer button 515 on the start screen 515 to enter a scheduling screen 530, as shown in FIG. 4b , to schedule a time period during which the mobile device 100 is automatically in inactive mode. Even further, as shown in FIG. 4c , the inactive mode may be automatically initiated upon the opening of a GPS/directions screen 540 of the mobile device. Yet even further, as shown in FIG. 4d , the inactive mode may be automatically initiated upon the pairing of the mobile device 100 and a vehicle, as shown by the Bluetooth device detection screen 550. Moreover, the inactive mode may be activated by a remote user 15, for example, to enable parents to limit distracted driving by teenagers. It is contemplated that any input that may indicate that the user is not to be distracted may be used to place the device in inactive mode, as will be understood by those of skill in the art.

Upon being placed in inactive mode, at step 402 the mobile device 100 may transmit an inactive mode begin notification 610 to the certification server 30. As shown in FIG. 8a , the inactive mode begin notification 610 may include a user identifier 620, and a begin timestamp 630 indicating the time that the inactive mode was initiated. Further, the inactive mode begin notification 610 may include a listing of functionality permissions 640 to record the functionality made available and/or the functionality made restricted to the user during the inactive mode. It is contemplated that the mobile device 100 need not immediately transmit the inactive mode begin notification 610 upon the step 401 of receiving an input to begin inactive mode is received, and the mobile device 100 may alternatively transmit the inactive mode begin notification 610 when requested, when a connection is available, during periods of low bandwidth utilization, or any other time useful to create the certification.

At step 403, the certification server 30 may receive an inactive mode begin notification 610. The certification server 30 may assume that inactive mode is operating continuously until receiving a signal, such as an inactive mode end notification 650 (FIG. 8b ), that inactive mode has been disabled. A certified record 670 of the data contained in the inactive mode begin notification 610 may be created and stored in a database of the certification server 30. As shown in FIG. 8c , the certified record 670 may include a first timestamp 680 of the time the inactive mode begin notification 610 was received.

At step 404, the mobile device 100 may suppress communications and enforce the restrictions of the inactive mode until the step 405 of receiving an input to end inactive mode. As previously described, an input may be the user pressing a button to end the inactive mode, the user scheduling a time period during which the mobile device 100 is automatically in inactive mode, the use of the driving directions functionality of the mobile device 100, activation by a remote user; etc.

At step 406, the mobile device 100 may transmit an inactive mode end notification 650 to the certification server 30 to indicate that the device 100 has left the inactive mode. The inactive mode end notification 650 may include a user identifier and a end timestamp 660 marking the time that the mobile device was removed from inactive mode. Further, the inactive mode end notification 650 may include a listing of functionality permissions 640 to record the functionality made available and/or the functionality made restricted to the user 15 during the inactive mode. It is contemplated that the mobile device 100 need not immediately transmit the inactive mode end notification 650 upon the step 405 of receiving an input to begin inactive mode is received, and the mobile device 100 may transmit the inactive mode end notification 650 when requested, when a connection is available, during periods of low bandwidth utilization, or any other time useful to create the certification.

At step 407, the certification server 30 may receive an inactive mode end notification 650. Upon receipt of the inactive mode end notification 650, the certification server 30 may make a certified record 670 of the inactive mode session. The certified record 670 of the inactive mode session may include the inactive mode begin notification 610, an inactive mode begin notification arrival timestamp 680 recording the arrival of the inactive mode begin notification 610, the inactive mode end notification 650, and an inactive mode end notification arrival timestamp 690 recording the arrival of the inactive mode end notification 650. In some embodiments, the certified record 670 may further include a GPS location trace of the mobile device 100 while the mobile device was in inactive mode. By storing a GPS location trace in the certified record, the user may, among other things, provide proof of location during inactive mode, as may be useful when an accident has occurred. The certified record 670 may be used to verify that the inactive mode was enabled during a period of time. To do so, the record may be made available via a user interface to the user 15, an insurance company, the police, the courts, a parent of the user 15, etc., to certify the times the device was in inactive mode and the restrictions on functionality in place during inactive mode.

In the embodiments of the inactive mode described above, the mobile device 100 may be initiated by the user 15 to suppress communications and enforce the restrictions of the inactive mode until the step of receiving an input to end inactive mode. In other embodiments, an inactive mode may be triggered on a per-communication or per-sender basis by one or more triggers 705 as shown in FIG. 9. An individual may define one or more triggers 705 to permit complex control of when the inactive mode is started and stopped. In this way, the triggers 705 may be rules that provide logic describing how the mobile device 100 is to respond to a communication.

FIG. 9 illustrates a trigger definition screen 700 to enable a user 15 to define triggers 705. As shown, the user 15 may select from various trigger types 707, such as a contact group triggers 710, time triggers 715, location triggers 720, and communication type triggers 725, when defining a trigger 705. Additionally, a user 15 may select to trigger on all communications using a suppress all selection box 735. When defining a trigger 705, a user 15 may select one or more criteria from one or more of the various trigger types 710.

As noted, one type of trigger types 707 may include contact groups 740 as may be enabled by a checkbox for the contact group trigger 710. Each contact of a user 15 may be classified in one or more contact groups 740. Triggers 705 may be defined that trigger based on the contact group 740 to which a sender 17 belongs. The user 15 may define the contact groups 740 and assign various senders 17 in his or her contact list to one or more caller groups 740 by pressing an edit button 742 for that contact group 740. Certain contact groups 740 may be pre-defined within the mobile application 141 and may be associated with pre-defined triggers 705, for example, senders 17 of a business contact group may have their communications suppressed outside of work hours, while senders 17 of a family contact group may have their communications transmitted normally.

Another trigger type 707 may be a time trigger 715 that triggers based on a time of the day. The mobile device 100 may include pre-defined triggers 705 based on the time of day, or the user 15 may define triggers 705 based on a time of day, such as lunch time, commute, dinner, nighttime, or any other arbitrary time period. For example, in an embodiment, a user 15 may define a sleep mode using triggers 705. In an example sleep mode, when the mobile device 100 detects that it is at a user-defined home, it rejects all calls and texts between predetermined hours, such as 10 p.m. and 7 a.m. The predetermined hours may be user configurable to accommodate various user schedules.

Yet another trigger type 707 may include a location trigger 720 that triggers based on the location of the mobile device 100. As an example, in an embodiment, the user 15 may define a dinner mode using triggers 705 to suppress communications during a family dinner. In an example dinner mode, when the mobile device 100 detects that it is at a user-defined home, it may reject all calls between configurable predetermined hours, such as 7 p.m. and 9 p.m. from all contact groups 710 except for a family contact group 710. As shown by the dinner mode example, various types of triggers may be combined as part of a rule.

Location triggers 720 may be triggered in a variety of ways. For example, the mobile device 100 may determine location by comparing the measured GPS location to a geofence. In another embodiment, location based triggers may trigger based on the proximity to other devices, such as a Wi-Fi network, I-beacon, Bluetooth beacon, etc. When adding a location trigger, the user may select a GPS location using a map, select a WiFi network name, and/or define a beacon to define the location.

A further type of trigger may include communication type trigger 725, that is, whether the communication is a text, call, etc. For example, in an embodiment, during dinner mode, texts may be transmitted through to the user 15, while calls and email notifications are suppressed.

Once the user 15 has defined the triggers 705 that will suppress a communication, the user 15 may set a response to the sender 17 that may be made when the communication is suppressed. As shown in FIG. 10 in a response definition screen 750, in an embodiment, the user 15 may select between no response (using a no response button 755), an SMS response (using the SMS response button 760), and an email response (using the email response button 765). For each type or response (or no response), the user may select the communication types that will trigger the response (using a communication type selection boxes 770). For an SMS or email response, the user 15 may input a response message 770 that is sent to the sender 17 as the response.

Triggers 705 enable users 15 to define communications that are to be suppressed by providing one or more trigger types 707. However, there are times when the user 15 may desire to avoid being generally interrupted, but may wish to receive important calls. Since placing the mode in inactive mode would suppress all communications, there is a need for functionality to permit selected communications to get through. Accordingly, the user may define various exceptions that permit a communication to get through, even when the mobile device is in inactive mode.

Exceptions 805 may be defined in the same manner as the triggers 705. As shown in FIG. 11, exceptions 805 may be defined in an add exceptions screen 780. The add exceptions screen 780 may permit the user 15 to define triggers 705 that permit otherwise suppressed communications to get through. As with the trigger definition screen 700, in an embodiment, the user 15 may select from various trigger types 707, such as a contact group triggers 710, time triggers 715, location triggers 720, and communication type triggers 725, when defining a trigger 705.

FIG. 12 illustrates a rules screen 800 that lists the inactive mode rules 802—such as triggers 705 and exceptions 805—that are currently active. As shown, rules 802 may define what communications 810 are affected (calls, emails, SMS, etc.), the time period 815 during which the rule 802 is active (Dinner time, work hours, etc.), the contact group 820 or groups the rule 802 applies to, and the location 825 at which the rule 802 is enforced. Not all rules 802 will include definitions for each of the communications 810, time period 815, contact groups 820, or location 825. For example, a rule 802 may be an exception 805 that permits calls from the family group to get through, regardless of the user's location.

Turning to FIG. 13, shown is an example of an inactive mode system 840 including a mobile device 100 of a user 15 and associated mobile devices 845 of associated users 847 that are associated with the user 15. Rules 802 on the mobile device 100 may suppress communications from senders 17. The rules 802 may be defined by the user 15, provided with the mobile application 141, or received from a remote server 850. As described further below, the user 15 may use the mobile device 100 to define rules 802 suppressing communications on the associated mobile devices 845.

In an embodiment, the mobile device 100 may receive rules 802, such as triggers 705, provided by remote servers 850 in communication with the mobile device. For example, a remote server 850 may receive the current location of the mobile device 100. The remote server 850 may determine that the mobile device 100 is within a geofence for a predefined rule 802. The remote server 850 may then provide the rule 802 to the mobile device 100, and, provided that the user has enabled push rules 802, may execute the rule 802. The remote server 850 may, in turn, receive rules 802 from client servers 851 or businesses 852.

For example, a theater may define a rule 802 that triggers when a mobile device 100 is on the theater premises. The rule 802 may suppress all calls and texts to the user 15 except, for example, from contacts part of a babysitter or emergency contact group 710. In this way, the owner of a theater may encourage the polite use of cell phones on the premises.

In an embodiment, the mobile application 100 may be used to turn on an inactive mode on another device. For example, as shown in FIG. 14, a parent may use a “homework mode” to control a child's receipt of calls, messages, emails, etc., on her device. In an embodiment, a parent may access a control screen 860 of their mobile device 100 to enter an inactive mode for an associated mobile device 845.

Using the control screen 860, the parent may limit the present types of communications the associated mobile device 845 of the child (the associated user 847) may receive. For example, the parent may turn on or off the text message functionality. In an embodiment, the associated mobile device 845 may include operating system level computer instructions that may intercept communications from senders 17 and suppress the intercepted communications. Additionally, while in inactive mode, outbound communications associated with the mobile device 845 may also be suppressed. Thus, the user of the associated mobile device 845 may be prevented from making or receiving communications.

Additionally, the parent may define one or more triggers 705 that control when the child may use certain functionality. For example, the parent may define a homework time from 7:00-9:00 pm on weekend nights when the child is at home to suppress all calls and text messages. The parent may create exceptions to the inactive mode on the associated mobile device 845 to permit the child to receive desired communications such as calls or texts from a Family contact group.

As shown in FIG. 14, the user 15 may first select the associated mobile device 845 using an associated device selection box 865. An active restrictions box 870 may list one or more triggers 705 that suppress communications on the selected associated mobile device 845, and the user 15 may scroll through the triggers 705 to view them all. An edit button 875 may permit the user to edit the triggers 705, or remove any of the triggers 705.

Additionally the user may add a trigger 705 to control communications on the associated mobile device 845. For example, as shown, the user 15 may define a trigger 705 by defining what communications 810 are affected (calls, emails, SMS, etc.), the time period 815 during which the rule 802 is active (Dinner time, work hours, etc.), the contact group 820 or groups the rule 802 applies to, and the location 825 at which the rule 802 is enforced. Additionally, the user 15 may enter a message 880 into a message box 885 that may be communicated to the associated user 847 when the inactive mode begins.

As shown in FIG. 15, when an inactive mode begins on an associated mobile device 845 in response to a trigger 705 defined on a mobile device 100, the associated mobile device 845 may alert the associated user 847 of the inactive mode. An alert box 890 may be displayed on the associated mobile device 845 and may include the message 880, along with details about the communications 810 that are suppressed, the time period 815, and the contacts groups 820 and the locations 825 affected, if any.

Turning to FIGS. 16 and 17, in an embodiment, the inactive mode may be triggered by automatic rule generation. For example, in an embodiment, generated rules 960, shown in the generated rules screen 950 of FIG. 17, may be automatically generated based on rules that trigger based on combinations of time, the location of the mobile device, a caller group of the caller, and various call events. As shown in the automatic rules configuration screen 900 in FIG. 16, the user 15 may enable automatic rule generation by checking a turn on automatic rules checkbox 905.

Automatic rule generation may be accomplished by the mobile application 141 based upon learning from the user's actions. For example, if a call comes through, the mobile device 100 may notify the user (by ringing, vibrating, etc.). The mobile application 141 may then record whether the call is answered or rejected by the user 15 pressing a silence button. A generated rule 960 may then be generated based on the user's behavior.

In an embodiment, a generated rule 960 may be generated in response to a minimum number of silence button presses from the user 15 makes and based on a set of thresholds the user provides. As shown in FIG. 16, the user 15 may provide a minimum silences threshold 910 in a minimum silences box 915. The user may additionally provide communication type thresholds 920, contact group thresholds 925, time period thresholds 930, and location thresholds 935.

The communication type thresholds 920 may be inputted using a slider that lets the user choose between generating generated rules 960 that apply to the “same type” of communications or “all types” of communications. When “same type” is chosen, then the minimum number of silences until a generated rule is automatically generated must all be silences of the same type (e.g., all calls, or all SMS, etc.). Alternatively, if “all types” is chosen, then any type of communication may count towards the minimum number of silences.

The contact group thresholds 925 may also be inputted using a slider that lets the user 15 choose between generating generated rules 960 that apply to a single sender 17, to a contact group 740, or to all contacts. When “single sender” is chosen, then the minimum number of silences until a generated rule 960 is created must be all from the same sender. Similarly, if “contact group” is selected, the minimum number of silences until a generated rule is created must be from the same contact group 740. Likewise, when “all contacts” is selected, then all senders 17 count towards the minimum number of silences.

The time period thresholds 930 may also be inputted using a slider that lets the user 15 chose between generating generated rules 960 that apply to a particular hour in the day, the current period, to periods on multiple days, or all times. When “same hour” is chosen, then the minimum number of silences must be from the same hour of the day (on any day). When “period” is chosen, then the minimum number of silences must be in the same period of the day on any day, wherein, in an embodiment, the same periods are morning, afternoon, evening, nighttime. When “work days” is chosen, the number of silences must be in the same period of the day on any day, where the same period is one of work hours, commute hours, evening hours, nighttime, weekend day time hours, and weekend night time hours. When “all times” is chosen, then there is no restriction on the time to satisfy the minimum number of silences.

The location thresholds 935 may also be inputted using a slider that lets the user 15 chose between generating generated rules 960 that apply to the “current location” or “all locations.” When “current location” is chosen, then only silences at the same location count towards the minimum number of silences. Conversely, when “all location” is chosen, then silences at any location may count towards the minimum number of silences.

As a first example, consider where the minimum number of silences is two, and the user has selected the “all types” communication type threshold, “contact group” contact group threshold 925, “work days” time period threshold 930, and the “all locations” location threshold 935. The user 15 silences four calls:

-   -   Call A: A call from a business contact in the evening on Tuesday         while at home     -   Call B: A SMS message from a business contact in the evening on         Wednesday while at a restaurant.     -   Call C: A call from a friend contact during the day on Thursday         while at work.     -   Call D: A SMS from a business member contact during the day on         Thursday while at work.

Applying the selected thresholds, the application 141 generates a rule from Call A and Call B, because both have the same contact group and the same time period, and the selected thresholds permit all types of communications and all types of locations. The application 141 does not generate a rule from any other combination of calls. For example, the pairings (Call A, Call C), (Call B, Call C), and (Call C, Call D) have different contact groups and therefore cannot combine to form a rule because of the “contact group” contact group threshold 925. Likewise, the pairings (Call A, Call C), (Call A, Call D), (Call B, Call C) and (Call B, Call D) have different time periods, and cannot combine to form a rule because of the “work days” time period threshold 930.

The user 15 may edit or delete the generated rules 960 using a generated rules screen 950. Each generated rule 965 may be deleted by pressing an associated trash can button 965. Alternatively, the user 15 may edit the generated rules by click an edit button 970 and selecting the generated rule 960 to edit. Generated rules 960 may be edited using the trigger definition screen 700 and each generated rule 960 may include all of the components of a trigger 705, including the call group 710, the time triggers 715, the location triggers 720, and communication type triggers 725.

Referring back to FIG. 2, the mobile device 100 includes a memory interface 102, one or more data processors, image processors and/or central processors 104, and a peripherals interface 106. The memory interface 102, the one or more processors 104 and/or the peripherals interface 106 can be separate components or can be integrated in one or more integrated circuits. The various components in the mobile device 100 can be coupled by one or more communication buses or signal lines, as will be recognized by those skilled in the art.

Sensors, devices, and additional subsystems can be coupled to the peripherals interface 106 to facilitate various functionalities. For example, a motion sensor 108 (e.g., a gyroscope), a light sensor 110, and a positioning sensor 112 (e.g., GPS receiver) can be coupled to the peripherals interface 106 to facilitate the orientation, lighting, and positioning functions described further herein. Other sensors 114 can also be connected to the peripherals interface 106, such as a proximity sensor, a temperature sensor, a biometric sensor, or other sensing device, to facilitate related functionalities.

A camera subsystem 116 and an optical sensor 118 (e.g., a charged coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) optical sensor) can be utilized to facilitate camera functions, such as recording photographs and video clips.

An audio subsystem 122 can be coupled to a speaker 124 and a microphone 126 to facilitate voice-enabled functions, such as voice recognition, voice replication, digital recording, and telephony functions.

The I/O subsystem 128 can include a touch screen controller 130 and/or other input controller(s) 132. The touch-screen controller 130 can be coupled to a touch screen 134. The touch screen 134 and touch screen controller 130 can, for example, detect contact and movement, or break thereof, using any of a plurality of touch sensitivity technologies, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen 134. The other input controller(s) 132 can be coupled to other input/control devices 136, such as one or more buttons, rocker switches, thumb-wheel, infrared port, USB port, and/or a pointer device such as a stylus. The one or more buttons (not shown) can include an up/down button for volume control of the speaker 124 and/or the microphone 126.

The memory interface 102 can be coupled to memory 138. The memory 138 can include high-speed random access memory and/or non-volatile memory, such as one or more magnetic disk storage devices, one or more optical storage devices, and/or flash memory (e.g., NAND, NOR). The memory 138 can store operating system instructions 140, such as Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks. The operating system instructions 140 may include instructions for handling basic system services and for performing hardware dependent tasks. In some implementations, the operating system instructions 140 can be a kernel (e.g., UNIX kernel).

The memory 138 may include graphical user interface instructions 144 to facilitate graphic user interface processing; sensor processing instructions 146 to facilitate sensor-related processing and functions; web browsing instructions 152 to facilitate web browsing-related processes and functions; media processing instructions 154 to facilitate media processing-related processes and functions; GPS/Navigation instructions 156 to facilitate GPS and navigation-related processes and instructions; camera instructions 158 to facilitate camera-related processes and functions; and/or other software instructions 160 to facilitate other processes and functions (e.g., access control management functions, etc.). The memory 138 may also store other software instructions (not shown) controlling other processes and functions of the mobile device 100 as will be recognized by those skilled in the art. In some implementations, the media processing instructions 154 are divided into audio processing instructions and video processing instructions to facilitate audio processing-related processes and functions and video processing-related processes and functions, respectively. An activation record and International Mobile Equipment Identity (IMEI) 162 or similar hardware identifier can also be stored in memory 138.

Each of the above identified instructions and applications can correspond to a set of instructions for performing one or more functions described herein. These instructions need not be implemented as separate software programs, procedures, or modules. The memory 138 can include additional instructions or fewer instructions. Furthermore, various functions of the mobile device 100 may be implemented in hardware and/or in software, including in one or more signal processing and/or application specific integrated circuits.

It should be noted that various changes and modifications to the presently preferred embodiments described herein will be apparent to those skilled in the art. Such changes and modifications may be made without departing from the spirit and scope of the present invention and without diminishing its attendant advantages. 

I claim:
 1. A mobile device, comprising: a wireless communication module; a processor, controlling the wireless communication module; and a memory controlled by the processor, the memory including instructions that when executed by the processor cause the processor to perform the steps of: providing a graphical user interface through which the controller receives a user selection to automatically initiate the inactive mode in response to the pairing of the mobile device with a vehicle; receiving a user selection of an away message to use when the mobile device is in inactive mode; in response to the pairing of the mobile device and the vehicle, automatically initiating a process to place the mobile device in inactive mode, when the mobile device is in inactive mode, in response to receiving a communication from the wireless communication module, transmitting the user selected away message via the wireless module and suppressing one or more sound, visual, or vibration communication cues that would have accompanied the communication had the mobile device not been in inactive mode; when the mobile device is placed in inactive mode, providing a notification to a certification server that the mobile device is in inactive mode; when the mobile device exits inactive mode, providing a notification to the certification server that the mobile device exited inactive mode; upon receipt of the notification that the mobile device exited inactive mode, the certification server creates a certified record of the inactive mode session including a user identification, a begin timestamp, an end timestamp, and a listing of functionality permissions that record the functionality made available and the functionality made restricted to the user during the time the mobile device was in inactive mode.
 2. The mobile device of claim 1 wherein the memory further includes instructions that when executed by the processor cause it to perform the step of: when the mobile device is in inactive mode, in response to receiving the communication from the wireless communication module, suppressing all sound, visual, and vibration communication cues that would have accompanied the communication had the mobile device not been in inactive mode.
 3. The mobile device of claim 1 wherein the memory further includes instructions that when executed by the processor cause it to perform the step of: providing a notification of the communications upon completion of the inactive mode.
 4. The mobile device of claim 1 wherein the communication received from the wireless communication module is an SMS message.
 5. The mobile device of claim 1 wherein the communication received from the wireless communication module is an email.
 6. The mobile device of claim 1 wherein the communication received from the wireless communication module is a cellular phone call.
 7. The mobile device of claim 1 wherein the user selected away message is a user customized away message. 